|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards-track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
This document specifies Atom, an XML-based Web content and metadata syndication format, including "author", "contributor" and "rights" definitions to handle owner information. This technique is used by H.IPTV-MD.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=4287
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Generally stable and well-understood; real implementation desirable but not necessary; no known technical flaws; considered immature; may be changed if problems are found or better solutions are identified; deploying implementation of such standards into a disruption-sensitive environment is not recommended.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Generally stable and well-understood; real implementation desirable but not necessary; no known technical flaws; considered immature; may be changed if problems are found or better solutions are identified; deploying implementation of such standards into a disruption-sensitive environment is not recommended.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[HTML] Raggett, D., Hors, A., and I. Jacobs, "HTML 4.01/
Specification", W3C REC REC-html401-19991224,/
December 1999,/
http://www.w3.org/TR/1999/REC-html401-19991224./
/
[MIMEREG] Freed, N. and J. Klensin, "Media Type Specifications and/
Registration Procedures", BCP 13, RFC 4288, December 2005./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2822] Resnick, P., "Internet Message Format", RFC 2822,/
April 2001./
/
[RFC2854] Connolly, D. and L. Masinter, "The 'text/html' Media/
Type", RFC 2854, June 2000./
/
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media/
Types", RFC 3023, January 2001./
/
[RFC3066] Alvestrand, H., "Tags for the Identification of/
Languages", BCP 47, RFC 3066, January 2001./
/
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:/
Timestamps", RFC 3339, July 2002./
/
[RFC3548] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 3548, July 2003./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66,/
RFC 3986, January 2005./
/
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource/
Identifiers (IRIs)", RFC 3987, January 2005./
/
[W3C.REC-xml-20040204]/
Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T.,/
and E. Maler, "Extensible Markup Language (XML) 1.0 (Third/
Edition)", W3C REC REC-xml-20040204, February 2004,/
http://www.w3.org/TR/2004/REC-xml-20040204./
/
[W3C.REC-xml-c14n-20010315]/
Boyer, J., "Canonical XML Version 1.0", W3C REC REC-xml-/
c14n-20010315, March 2001,/
http://www.w3.org/TR/2001/REC-xml-c14n-20010315./
/
[W3C.REC-xml-exc-c14n-20020718]/
Eastlake, D., Boyer, J., and J. Reagle, "Exclusive XML/
Canonicalization Version 1.0", W3C REC REC-xml-exc-c14n-/
20020718, July 2002,/
http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718./
/
[W3C.REC-xml-infoset-20040204]/
Cowan, J. and R. Tobin, "XML Information Set (Second/
Edition)", W3C REC REC-xml-infoset-20040204,/
February 2004,/
http://www.w3.org/TR/2004/REC-xml-infoset-20040204./
/
[W3C.REC-xml-names-19990114]/
Hollander, D., Bray, T., and A. Layman, "Namespaces in/
XML", W3C REC REC-xml-names-19990114, January 1999,/
http://www.w3.org/TR/1999/REC-xml-names-19990114./
/
[W3C.REC-xmlbase-20010627]/
Marsh, J., "XML Base", W3C REC REC-xmlbase-20010627,/
June 2001,/
http://www.w3.org/TR/2001/REC-xmlbase-20010627./
/
[W3C.REC-xmldsig-core-20020212]/
Solo, D., Reagle, J., and D. Eastlake, "XML-Signature/
Syntax and Processing", W3C REC REC-xmldsig-core-20020212,/
February 2002,/
http://www.w3.org/TR/2002/REC-xmldsig-core-20020212./
/
[W3C.REC-xmlenc-core-20021210]/
Reagle, J. and D. Eastlake, "XML Encryption Syntax and/
Processing", W3C REC REC-xmlenc-core-20021210,/
December 2002,/
http://www.w3.org/TR/2002/REC-xmlenc-core-20021210./
/
[XHTML] Altheim, M., Boumphrey, F., McCarron, S., Dooley, S.,/
Schnitzenbaumer, S., and T. Wugofski, "Modularization of/
XHTML[TM]", W3C REC REC-xhtml-modularization-20010410,/
April 2001, http://www.w3.org/TR/2001//
REC-xhtml-modularization-20010410./
/
Informative References/
[ISO.8601.1988]/
International Organization for Standardization, "Data/
elements and interchange formats - Information interchange/
- Representation of dates and times", ISO Standard 8601,/
June 1988./
/
[RELAX-NG] Clark, J., "RELAX NG Compact Syntax", December 2001,/
http://www.oasis-open.org/committees/relax-ng//
compact-20021121.html./
/
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 2434,/
October 1998./
/
[W3C.NOTE-datetime-19980827]/
Wolf, M. and C. Wicksteed, "Date and Time Formats", W3C/
NOTE NOTE-datetime-19980827, August 1998,/
http://www.w3.org/TR/1998/NOTE-datetime-19980827./
/
[W3C.REC-xmlschema-2-20041028]/
Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes/
Second Edition", W3C REC REC-xmlschema-2-20041028,/
October 2004,/
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
